This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Does "ReCache" work as described? ~Umberto Nongeroson 21.Aug.03 11:27 PM a Web browser Applications Development 6.0.1 CF1Windows 98
I just tried it, and it seems to work just fine in a CWC field as best I can tell; i.e. it works the same as NoCache for the initial lookup. I didn't check whether it was really updating the cache, when used in a CWC field, but I tried it in an agent and it is definitely updating the cache in that case.
Perhaps you shoul dbe more specific about what it's doing wrong and what you expected.
As I read the documentation, ReCache is the same as NoCache except that the value it reads is left in the cache afterwards. So, it'll read the database every time, but if you do the same lookup later without specifying a caching option, the result will be up to date as of the last ReCache.
The way I see it, "ReCache" is useful if you have some idea that the same lookup will be done by a different formula at a later time. For instance, suppose you have an application that does an @DbColumn keyword list ("Customers" view). The user has an option, to create a new customer. If they then use the form that contains the keyword lookup, they would expect to see the new customer on that list. The old way was, either you use NoCache each time, which causes unnecessary delay in the 99.3% of cases where there is not a new customer, or use "" and tell the users to exit the database each time they add one (or you could do some more complex stuff, like setting fields in a profile document with a list of additional customers, which has to be added in each time the keyword list is calculated).
With "ReCache" you can make it better in a couple of different ways -- one, when the user creates or edits a customer document, you can have the Postsave event do the same @DbColumn lookup that you know is used elsewhere, using ReCache. And/or, you can add a control on the form containing the keyword field that lets the user explicitly refresh choices, in case they believe someone else entered the new information.
Return to top
. . RE: Does "ReCache" work as describe... (~Bill Frokimari... 21.Aug.03) 
Print this page
